You may wonder why I keep coming back to this beast, when I keep saying that I won't. Here is the answer:
Summary of Operations Net Sales $481,701 $460,192 $443,795 $429,732 $409,173 Gross profit margin 156,787 149,084 145,782 146,823 140,362 Interest expense 7,902 8,269 6,761 5,422 4,623 Income before income taxes 32,620 34,766 35,551 22,422 29,666 Provision for income taxes 12,444 13,043 13,267 9,334 12,311 Net income* 20,176 22,723 22,284 13,088 17,355
Per Share Data Earnings* 2.10 2.23 2.01 1.10 1.41 Dividends paid .71 .67 .60 .55 .52 Book value 15.42 14.67 13.32 13.71 13.05 Average shares outstanding 9,629 10,212 11,113 11,929 12,350
June 30 Financial Condition Working capital 104,285 115,222 107,905 107,575 109,934 Current ratio 2.43 2.72 2.75 2.89 3.23 Property, plant and equipment - net 86,182 85,870 82,011 83,314 85,627 Total assets 297,418 297,849 277,114 276,187 266,988 Long-term debt 70,133 72,978 64,979 48,786 45,851 Stockholders' equity 138,688 142,406 137,142 156,429 159,664
If you see anything that looks even _remotely_ like a financial table in there, you're the first...
And: luck is what happens to people who plan ahead: I was lucky enough to have wanted a second wildstring before I _needed_ it. There are pages upon pages of this crap, and it would have taken many error-prone hours to fix it. I got within shooting range with this:
^~^#^*^+ ^~^#^*^p^+
which says, in case you can't interpret Torquemada when he's speaking in tongues, "soak up everything to the first digit, then soak up everything to the next capital letter; pump out everything up to the first number, the number, everything up the the first cap, a return, and then the cap". I don't think this could be done at all with any Torque before this one, and it certainly couldn't be done in one string. I used four more sets to get this junk into its final, expiatable form, but _this_ is the Inquisitor's finest hour. If I can't burn the idiots who send stuff like this and say "it's all on disk," at least I can burn through their files. Of course, they'll pay for what it _would_ have and _should_ have cost, not what it did cost. Thus do we sustain the entrepreneurial spirit of innovation (grin).
Now, then: what's new?
But one thing, but it's a biggie: another wildstring, like ^*. This one is ^~, and it means exactaly what ^* means, soak up everything until the pattern matches. The two can be used together in the same string, and they can be resequenced on the replace side. A second wildstring isn't half as useful as the first one was, but when it _is_ useful, it's indispensible. A nice use for it is shown in the Code Alternating Paragraphs set enclosed. The above search string is also shown as a set in the file What Idiots!.
Two other changes: first, this version should run flawlessly on all Macs with 128K ROMs or above. The stack has been bumped hugely. This has two consequences: 1. the partition is increased to 768K, and 2. we are operating on 16-times as much as we were, per buffer. That means that most typical files will find redemption in one buffer, which makes buffer-related errors much less likely. Buffer-related errors: ^* followed by nothing _sounds_ like it means "to the end of the file". What it means to the Inquisitor is "to the end of the buffer". Buffer-bounding problems do not happen with ordinary wildcards, since we are trapping for them. But the wildstrings can be any length, up to the full size of the buffer (more memory than my first four computers); it is impossible to trap for them _and_ reliably process text. So: if you used Code Alternating Paragraphs on a file with paragraphs larger than 256 bytes, you risk buffer-related errors. Torque is helping you avoid this by making the buffer so enormous. Help yourself by making sure your use of wildstrings falls within the bounds Torquemada can permit.
Second, I made some changes to the way Torquemada is interpreting the pattern after a wildstring. Before, I was looking for a full match to the pattern only at the first sighting of the character after the wildstring (what I referred to in the release notes as the terminator). This was bad logic. Now I am looking at every instance of the terminator and _then_ comparing to the rest of the pattern. It's a failure only if it fails all the way to the end of the buffer. Here's what I mean:
The search string is:
Greg^*^pchattering
The copy:
Greg Swann
chattering
would score a hit with both TQM 1.0.6 and 1.0.7, but
Greg Swann
chattering
would fail under 1.0.6, even though it matches the pattern.
Serendipitous fallout from change: you can use ^0 ... ^9 in the pattern after a wildstring. I still don't think it's such a sweet idea, and, of course, you can't (intelligibly) use one of these _immediately_ after a wildstring.
That's all, and that's _it_, I _swear_...
Greg Swann
4/15/92
TORQUEMADA QUICK REFERENCE
Aliases
^t or ^T Tab
^p or ^P Return
^^ Caret
Untyped wildcards (match any one character)
^0
^1
etc.,
through
^9
Typed wildcards (match any one character _of their type_)
^! Punctuation
^# Digit
^_ Space (spaceband, tab, return or option-space)
^+ Uppercase character
^- Lowercase character
^± Character of either case
Wildstrings (match and store runs of characters until pattern is matched)
